fix memory render#1087
Conversation
|
Claude finished @ishaanxgupta's task in 40s —— View job PR Review Complete
Overview: Simplifies edge source/target node lookup by reusing already-computed Issues found: None — this looks good to ship. The change in
The version bump from 0.2.2 → 0.2.3 is appropriate for this fix. Score: 10/10 |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-mcp | a87c932 | Jun 13 2026, 07:29 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | a87c932 | Commit Preview URL Branch Preview URL |
Jun 13 2026, 07:30 AM |
Removed outdated comments regarding edge source/target resolution.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview: Simplifies edge source/target node lookup by reusing the already-computed srcId/tgtId variables instead of redundant type checking.
Issues found: None — this looks good to ship.
The change correctly leverages the existing type handling at lines 227-228 where srcId and tgtId are extracted. The old code duplicated this type check unnecessarily. The new code is cleaner and always looks up nodes from nodeMap, which is actually safer as it ensures consistent node references rather than potentially using stale objects stored directly in edge data.
Score: 10/10
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Apply changes from code browser
1 participant
No description provided.